Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cae7173c3ff9ab5fd1171d0afae1506f77ebe4f5b8b2426c30021da7009570a

Tx prefix hash: d81a588d342cddc01b70e4c23d20377f9bab56c347a9bfa8251a23eed623511d
Tx public key: 17784d73062cd5eabd7e453894339278d2d91d36bb41b6f4daa08c0e33028df6
Timestamp: 1751309229 Timestamp [UCT]: 2025-06-30 18:47:09 Age [y:d:h:m:s]: 00:136:15:59:13
Block: 1316029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95864 RingCT/type: yes/0
Extra: 0117784d73062cd5eabd7e453894339278d2d91d36bb41b6f4daa08c0e33028df6021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd9f8d95a9dd2bbbbe6bcab7ba34ad3cf7be8a0debf929dc1a4f5d8de8bb5eec 0.600000000000 1803686 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": 1316039, "vin": [ { "gen": { "height": 1316029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd9f8d95a9dd2bbbbe6bcab7ba34ad3cf7be8a0debf929dc1a4f5d8de8bb5eec" } } ], "extra": [ 1, 23, 120, 77, 115, 6, 44, 213, 234, 189, 126, 69, 56, 148, 51, 146, 120, 210, 217, 29, 54, 187, 65, 182, 244, 218, 160, 140, 14, 51, 2, 141, 246, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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