Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e4a746bc5f9afe3eda02554f1995de37d5509fd1bec2da8b6c6614f7beadec5

Tx prefix hash: 8aef8aa7c182200b432436cebafca2704f3cb8860c49e249a092f9b92d9c9939
Tx public key: 050b50d85db52edfc0e5177a2fdc56cd55af64c430986c4a52909cb217f4f88f
Timestamp: 1711773382 Timestamp [UCT]: 2024-03-30 04:36:22 Age [y:d:h:m:s]: 01:079:16:58:46
Block: 989374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317834 RingCT/type: yes/0
Extra: 01050b50d85db52edfc0e5177a2fdc56cd55af64c430986c4a52909cb217f4f88f02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 846bf2b5b03c297b327d1a5dc5e4e16c0ed68ee64d0d0ab3721e0ac33dc3b90d 0.600000000000 1449671 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": 989384, "vin": [ { "gen": { "height": 989374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "846bf2b5b03c297b327d1a5dc5e4e16c0ed68ee64d0d0ab3721e0ac33dc3b90d" } } ], "extra": [ 1, 5, 11, 80, 216, 93, 181, 46, 223, 192, 229, 23, 122, 47, 220, 86, 205, 85, 175, 100, 196, 48, 152, 108, 74, 82, 144, 156, 178, 23, 244, 248, 143, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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