Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657f7bdb31c9aec1678791cc99155d308996d1b14c4ac697c8fcc276fed9cf0c

Tx prefix hash: e55e5f500cadb134680e6baa020bf911b74f0bc7fd7aa182d86d8e076599a6fe
Tx public key: ed4f28dd186ce3237765823a754e7a02bf56c2f7a9978182db2530a42e43b967
Timestamp: 1771512105 Timestamp [UTC]: 2026-02-19 14:41:45 Age [y:d:h:m:s]: 00:273:11:10:52
Block: 1481264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201048 RingCT/type: yes/0
Extra: 01ed4f28dd186ce3237765823a754e7a02bf56c2f7a9978182db2530a42e43b967021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 741dec791186133e0d3555a6bf840f3a23d4fda6c1277ae83f247664d74e298f 0.000600000000 1970640 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": 1481274, "vin": [ { "gen": { "height": 1481264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "741dec791186133e0d3555a6bf840f3a23d4fda6c1277ae83f247664d74e298f" } } ], "extra": [ 1, 237, 79, 40, 221, 24, 108, 227, 35, 119, 101, 130, 58, 117, 78, 122, 2, 191, 86, 194, 247, 169, 151, 129, 130, 219, 37, 48, 164, 46, 67, 185, 103, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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