Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9d08c02c9fb56a788c3d5c718122f6503b070342ef82eccd0b6339a9ac372d1

Tx prefix hash: d1e13276df02c84ab0bfe7c4946fee676a5b952c141c64a0b8fe776f511d0364
Tx public key: 674b6e6e549babdf214ae62d906f593abfdac863548c6953dfc296b681a0e775
Timestamp: 1735368031 Timestamp [UCT]: 2024-12-28 06:40:31 Age [y:d:h:m:s]: 00:134:04:57:57
Block: 1184839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95727 RingCT/type: yes/0
Extra: 01674b6e6e549babdf214ae62d906f593abfdac863548c6953dfc296b681a0e7750211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dab27d04070b334d6cd4827622ece563322a3ac1db6275fcab3b9b7edd1a302 0.600000000000 1671298 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": 1184849, "vin": [ { "gen": { "height": 1184839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dab27d04070b334d6cd4827622ece563322a3ac1db6275fcab3b9b7edd1a302" } } ], "extra": [ 1, 103, 75, 110, 110, 84, 155, 171, 223, 33, 74, 230, 45, 144, 111, 89, 58, 191, 218, 200, 99, 84, 140, 105, 83, 223, 194, 150, 182, 129, 160, 231, 117, 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