Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7a6d634ba8716f3136280dde382a97aeb678b05fa804412955e831f5f74db9b

Tx prefix hash: 310c6e2d5a3e4c1e0d77e4347345e8d66666ab01efa0f46d24a2537bebd9078c
Tx public key: 4147ac2e864a6e858e791da3d81c2d21e811a2ae28386b20b11b0d1a63ff7b86
Timestamp: 1750586523 Timestamp [UCT]: 2025-06-22 10:02:03 Age [y:d:h:m:s]: 00:147:06:35:07
Block: 1310376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103119 RingCT/type: yes/0
Extra: 014147ac2e864a6e858e791da3d81c2d21e811a2ae28386b20b11b0d1a63ff7b86021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc493cb61ce248e8b7b1c00368e3a81f9c8bcead1c82547f01b546d5a5d9d52c 0.600000000000 1797995 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": 1310386, "vin": [ { "gen": { "height": 1310376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc493cb61ce248e8b7b1c00368e3a81f9c8bcead1c82547f01b546d5a5d9d52c" } } ], "extra": [ 1, 65, 71, 172, 46, 134, 74, 110, 133, 142, 121, 29, 163, 216, 28, 45, 33, 232, 17, 162, 174, 40, 56, 107, 32, 177, 27, 13, 26, 99, 255, 123, 134, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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