Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cafae75fef84fd432453e1c525ddcbcddf18992804e75717cda676b2fee0187

Tx prefix hash: 6e0fa5d09991b78a2e6cdde493c569376534a5f10df4507b78029c06eeb32d72
Tx public key: 8c2b5be55f4ff46bfac7a32313a33dcd61b927adcd661a0db7c9e0f387aad258
Timestamp: 1705084207 Timestamp [UCT]: 2024-01-12 18:30:07 Age [y:d:h:m:s]: 01:301:08:34:36
Block: 933879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474200 RingCT/type: yes/0
Extra: 018c2b5be55f4ff46bfac7a32313a33dcd61b927adcd661a0db7c9e0f387aad25802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad2f06c93366205cbdf37210a5c2ef3a8d9766c6d44ab74d6168b39765b2894f 0.600000000000 1391863 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": 933889, "vin": [ { "gen": { "height": 933879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad2f06c93366205cbdf37210a5c2ef3a8d9766c6d44ab74d6168b39765b2894f" } } ], "extra": [ 1, 140, 43, 91, 229, 95, 79, 244, 107, 250, 199, 163, 35, 19, 163, 61, 205, 97, 185, 39, 173, 205, 102, 26, 13, 183, 201, 224, 243, 135, 170, 210, 88, 2, 17, 0, 0, 0, 4, 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