Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722900e7b46c5c9f5055c9fc43fbcad388df50739c00acf88bf6f38968cb6f6d

Tx prefix hash: b210e02b0635a54aece3a6d50d809af5332135787b50e99080988ccbbdf3be94
Tx public key: a1f66f1dc28f79a7f86ceac0cccfb4a834dd56430efa73191b1721b092ea365f
Timestamp: 1760478256 Timestamp [UCT]: 2025-10-14 21:44:16 Age [y:d:h:m:s]: 00:025:06:08:51
Block: 1390025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18082 RingCT/type: yes/0
Extra: 01a1f66f1dc28f79a7f86ceac0cccfb4a834dd56430efa73191b1721b092ea365f021100000008df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64206bdcb9b929374e60ddc7a4b4402620c6322f99bf5c6d64c1cf13e3b3e52b 0.600000000000 1878256 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 dinasty-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": 1390035, "vin": [ { "gen": { "height": 1390025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64206bdcb9b929374e60ddc7a4b4402620c6322f99bf5c6d64c1cf13e3b3e52b" } } ], "extra": [ 1, 161, 246, 111, 29, 194, 143, 121, 167, 248, 108, 234, 192, 204, 207, 180, 168, 52, 221, 86, 67, 14, 250, 115, 25, 27, 23, 33, 176, 146, 234, 54, 95, 2, 17, 0, 0, 0, 8, 223, 90, 36, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8