Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74df1eaba931f5d06203d4ba6fea88a103a29a0a7f0efccc8e6163b768227fc1

Tx prefix hash: fc3b7c5f3a706630dbceca72bc09c73f755f8aea71c27b5d1aa87d5bcd46f98c
Tx public key: 7fe39293082b78c0af20649c4ace1a7eb4d0e2f7b25aa34aa6da6b0bc97e942f
Timestamp: 1736522377 Timestamp [UCT]: 2025-01-10 15:19:37 Age [y:d:h:m:s]: 00:104:13:02:39
Block: 1194392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74509 RingCT/type: yes/0
Extra: 017fe39293082b78c0af20649c4ace1a7eb4d0e2f7b25aa34aa6da6b0bc97e942f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42ef378e7e87b9b13497ac02009f1ef923722423835c3322d4b574852970f963 0.600000000000 1680963 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": 1194402, "vin": [ { "gen": { "height": 1194392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42ef378e7e87b9b13497ac02009f1ef923722423835c3322d4b574852970f963" } } ], "extra": [ 1, 127, 227, 146, 147, 8, 43, 120, 192, 175, 32, 100, 156, 74, 206, 26, 126, 180, 208, 226, 247, 178, 90, 163, 74, 166, 218, 107, 11, 201, 126, 148, 47, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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