Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c393e101ff66f0f34e2a989c12df79a093e390c95e40500d9d43e5fc52b21ea1

Tx prefix hash: 3569303a8c2154842967d46b84f37a59dda75e81e0ecf56d0cfd5ebb1de9259b
Tx public key: 9c77360320a9b635ae548757535f00adc2fb826a8eeb88ad0e7e29c462b1391a
Timestamp: 1714669926 Timestamp [UCT]: 2024-05-02 17:12:06 Age [y:d:h:m:s]: 01:194:22:38:53
Block: 1013370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397954 RingCT/type: yes/0
Extra: 019c77360320a9b635ae548757535f00adc2fb826a8eeb88ad0e7e29c462b1391a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e30747e2c5d4abdbd86df8174a7215c33fcc475985c08e01f75fd71988fc3c80 0.600000000000 1476169 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": 1013380, "vin": [ { "gen": { "height": 1013370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30747e2c5d4abdbd86df8174a7215c33fcc475985c08e01f75fd71988fc3c80" } } ], "extra": [ 1, 156, 119, 54, 3, 32, 169, 182, 53, 174, 84, 135, 87, 83, 95, 0, 173, 194, 251, 130, 106, 142, 235, 136, 173, 14, 126, 41, 196, 98, 177, 57, 26, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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