Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23c52cfadb1c1bbed529f265b94bd6375c9b8a9b3de3ded734a3f26ffc896864

Tx prefix hash: 239b873c68d6fdc0a92196e173e233a21dbc8b7112b1bca806e0c7beb989e527
Tx public key: 5248ccebc431f46650072b0f02091b960ab003cc93a8c08d1e3f2d763fb063e8
Timestamp: 1765411077 Timestamp [UCT]: 2025-12-10 23:57:57 Age [y:d:h:m:s]: 00:011:09:00:55
Block: 1430904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8135 RingCT/type: yes/0
Extra: 015248ccebc431f46650072b0f02091b960ab003cc93a8c08d1e3f2d763fb063e8021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6a1fa4cef1a021ff438c89e97244419ca10d0ca0fc549ce2eda14b7837d3e28 0.600000000000 1919657 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": 1430914, "vin": [ { "gen": { "height": 1430904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6a1fa4cef1a021ff438c89e97244419ca10d0ca0fc549ce2eda14b7837d3e28" } } ], "extra": [ 1, 82, 72, 204, 235, 196, 49, 244, 102, 80, 7, 43, 15, 2, 9, 27, 150, 10, 176, 3, 204, 147, 168, 192, 141, 30, 63, 45, 118, 63, 176, 99, 232, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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