Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cdcb4e6cb9cec355122d697061da27d54f283b35bc714c87b044f04a9cc3228

Tx prefix hash: ac1fab18d32d89529e0f5f4575f88141244bbbc02fd2f2d1efa79772dbef72b2
Tx public key: 182fbddcf08654f7870302adb30db50ca2f881ad7d50e9c69f6a65a57bde484b
Timestamp: 1584634834 Timestamp [UCT]: 2020-03-19 16:20:34 Age [y:d:h:m:s]: 04:326:11:43:12
Block: 85501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129036 RingCT/type: yes/0
Extra: 01182fbddcf08654f7870302adb30db50ca2f881ad7d50e9c69f6a65a57bde484b0211000001f0e1f32f7d000000000000000000

1 output(s) for total of 319.668965597000 dcy

stealth address amount amount idx
00: ee25ead3be59d30b801e2f1c142fc8609b31be3bc1f73b5731eef32ba2d4e082 319.668965597000 154525 of 0

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": 85511, "vin": [ { "gen": { "height": 85501 } } ], "vout": [ { "amount": 319668965597, "target": { "key": "ee25ead3be59d30b801e2f1c142fc8609b31be3bc1f73b5731eef32ba2d4e082" } } ], "extra": [ 1, 24, 47, 189, 220, 240, 134, 84, 247, 135, 3, 2, 173, 179, 13, 181, 12, 162, 248, 129, 173, 125, 80, 233, 198, 159, 106, 101, 165, 123, 222, 72, 75, 2, 17, 0, 0, 1, 240, 225, 243, 47, 125, 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