Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13ebaabfae6523fc4ac05bc6da33f0647b1a45f78338ce0bacaf7ac27ba4d143

Tx prefix hash: e755b9f3238b321748a62e6f1e124fb7e2e70ce96acf7bdeb2af6d8ee75d7d24
Tx public key: 6ead2b7ce1a7e0283f4c2951206277381b319ca0b5714d842060cf39e878cb41
Timestamp: 1711828121 Timestamp [UCT]: 2024-03-30 19:48:41 Age [y:d:h:m:s]: 01:069:11:17:08
Block: 989827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310640 RingCT/type: yes/0
Extra: 016ead2b7ce1a7e0283f4c2951206277381b319ca0b5714d842060cf39e878cb410211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a404524ac7d4ff7105219f9d49b494f7cafbb0eed73d6aa61b3c81e6cd5bdb99 0.600000000000 1450145 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": 989837, "vin": [ { "gen": { "height": 989827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a404524ac7d4ff7105219f9d49b494f7cafbb0eed73d6aa61b3c81e6cd5bdb99" } } ], "extra": [ 1, 110, 173, 43, 124, 225, 167, 224, 40, 63, 76, 41, 81, 32, 98, 119, 56, 27, 49, 156, 160, 181, 113, 77, 132, 32, 96, 207, 57, 232, 120, 203, 65, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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