Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dbd17d659d5a80a3661b615e42b3992c2e4f69f4a88c555a4260cb20b69dcd8

Tx prefix hash: d8280f74ef72eb0788475e75afc4ae7bb3e3b45379edcf76097bd53786721d4d
Tx public key: 5231177eacbfdbad69d1b1b87e38c55009ae389a1be9437c1aaf416d89bf60d6
Timestamp: 1732497064 Timestamp [UCT]: 2024-11-25 01:11:04 Age [y:d:h:m:s]: 00:136:04:07:35
Block: 1161063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97140 RingCT/type: yes/0
Extra: 015231177eacbfdbad69d1b1b87e38c55009ae389a1be9437c1aaf416d89bf60d602110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42233e4ab7a998d4700dfd48fcebb4eb2bb1d7b89dcd6ed8a9bab7e35b146d3e 0.600000000000 1646714 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": 1161073, "vin": [ { "gen": { "height": 1161063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42233e4ab7a998d4700dfd48fcebb4eb2bb1d7b89dcd6ed8a9bab7e35b146d3e" } } ], "extra": [ 1, 82, 49, 23, 126, 172, 191, 219, 173, 105, 209, 177, 184, 126, 56, 197, 80, 9, 174, 56, 154, 27, 233, 67, 124, 26, 175, 65, 109, 137, 191, 96, 214, 2, 17, 0, 0, 0, 15, 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