Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffb0d87773c7305ef2044e8b6063166a46ba009da4cf854fcf27ea78b5ee1b4a

Tx prefix hash: 77e699a2f41e424a8e1dee8862576be630b0b09cb2c70abbc2b50612927861d2
Tx public key: 65274fb43a51c614b2f3e7b92cbc7f4df775a31247b857ab0459d7c3d366e7f0
Timestamp: 1774732329 Timestamp [UTC]: 2026-03-28 21:12:09 Age [y:d:h:m:s]: 00:234:14:36:43
Block: 1507904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173205 RingCT/type: yes/0
Extra: 0165274fb43a51c614b2f3e7b92cbc7f4df775a31247b857ab0459d7c3d366e7f0021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3b6204921048a3895c28aaa91aa53c84402b5a5a273f9c08ed7f29fc2dd99ff6 0.000600000000 1997656 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": 1507914, "vin": [ { "gen": { "height": 1507904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b6204921048a3895c28aaa91aa53c84402b5a5a273f9c08ed7f29fc2dd99ff6" } } ], "extra": [ 1, 101, 39, 79, 180, 58, 81, 198, 20, 178, 243, 231, 185, 44, 188, 127, 77, 247, 117, 163, 18, 71, 184, 87, 171, 4, 89, 215, 195, 211, 102, 231, 240, 2, 17, 0, 0, 0, 1, 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: