Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4dc981d93fe0f2c7ff7f0e6ee6e9838adf4fd644043f1aacacbe744397f43e2

Tx prefix hash: f1f6303caa6e9403e236bc33e1ac7be233b4ea5f98971f3452776bcb9916bec2
Tx public key: c74fe303d6cc76516709e59cbbc139a5afb988739befe5e00324bc61314aac2c
Timestamp: 1729477929 Timestamp [UCT]: 2024-10-21 02:32:09 Age [y:d:h:m:s]: 00:165:23:46:21
Block: 1136088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118444 RingCT/type: yes/0
Extra: 01c74fe303d6cc76516709e59cbbc139a5afb988739befe5e00324bc61314aac2c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cd0bb0124fc38b1ce9313eec9e2b6a210c3c2ba23c9c19d7b871f3f38d384d7 0.600000000000 1619431 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": 1136098, "vin": [ { "gen": { "height": 1136088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cd0bb0124fc38b1ce9313eec9e2b6a210c3c2ba23c9c19d7b871f3f38d384d7" } } ], "extra": [ 1, 199, 79, 227, 3, 214, 204, 118, 81, 103, 9, 229, 156, 187, 193, 57, 165, 175, 185, 136, 115, 155, 239, 229, 224, 3, 36, 188, 97, 49, 74, 172, 44, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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