Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 347d4839a48a341ea2b976d482fa7abedf3609c7855194413838b8284e7d231c

Tx prefix hash: 862205ec3b9d63a4c48405cdc28931b74444069222ae2cec0f5d1ab6c9301ea1
Tx public key: 9cdfdece1580d511b9e71d4b6bd9fe4d039eb0c42c357365b0c91fae2e64879d
Timestamp: 1751277085 Timestamp [UCT]: 2025-06-30 09:51:25 Age [y:d:h:m:s]: 00:139:00:51:08
Block: 1315764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97558 RingCT/type: yes/0
Extra: 019cdfdece1580d511b9e71d4b6bd9fe4d039eb0c42c357365b0c91fae2e64879d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6fa702b8a53a9fc4c23e442c9617994eeecb60ec4de73b85ea34ba79a393e81 0.600000000000 1803419 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": 1315774, "vin": [ { "gen": { "height": 1315764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6fa702b8a53a9fc4c23e442c9617994eeecb60ec4de73b85ea34ba79a393e81" } } ], "extra": [ 1, 156, 223, 222, 206, 21, 128, 213, 17, 185, 231, 29, 75, 107, 217, 254, 77, 3, 158, 176, 196, 44, 53, 115, 101, 176, 201, 31, 174, 46, 100, 135, 157, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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