Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fea3e60b36a24a643487213a75c379d687026d639ca0570f27d8b4246129be02

Tx prefix hash: 230d594640ac2a802398ce4d1b946466e186e871e3345ed9364afb564cbcb56a
Tx public key: 0f140db379fb6e86f3e3cb3076bf8500c6d68a0d61eae1eb9d3e5e4aed4fb13c
Timestamp: 1770323600 Timestamp [UTC]: 2026-02-05 20:33:20 Age [y:d:h:m:s]: 00:009:00:00:36
Block: 1471454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 6406 RingCT/type: yes/0
Extra: 010f140db379fb6e86f3e3cb3076bf8500c6d68a0d61eae1eb9d3e5e4aed4fb13c0208099ff24767d61948

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 43a6743b102f440d6a7e4996b9e5f9ea85c325331518ff08ae5c5fa3af5cac5d 0.000600000000 1960726 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1471464, "vin": [ { "gen": { "height": 1471454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43a6743b102f440d6a7e4996b9e5f9ea85c325331518ff08ae5c5fa3af5cac5d" } } ], "extra": [ 1, 15, 20, 13, 179, 121, 251, 110, 134, 243, 227, 203, 48, 118, 191, 133, 0, 198, 214, 138, 13, 97, 234, 225, 235, 157, 62, 94, 74, 237, 79, 177, 60, 2, 8, 9, 159, 242, 71, 103, 214, 25, 72 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369