Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37161255c90a4c8d71aa159fc7e35d889917ddc420fc37bceaf9f72145192309

Tx prefix hash: 345a732942781dfbeadd13bd58bde5753a96db4f80f258c9ad9e752a93c6f5bb
Tx public key: ae4d29b84f1656aeae781f0d12c7fbd4cf12540fd0172e2ca798d6b09a20e805
Timestamp: 1582339969 Timestamp [UCT]: 2020-02-22 02:52:49 Age [y:d:h:m:s]: 05:100:10:31:35
Block: 69994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1224950 RingCT/type: yes/0
Extra: 01ae4d29b84f1656aeae781f0d12c7fbd4cf12540fd0172e2ca798d6b09a20e805021100000001026b59f3000000000000000000

1 output(s) for total of 359.816956521000 dcy

stealth address amount amount idx
00: d305dc70ae8d427970c930e44ce51166ee22eae2c3df32338314589f15fb9c85 359.816956521000 129154 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": 70004, "vin": [ { "gen": { "height": 69994 } } ], "vout": [ { "amount": 359816956521, "target": { "key": "d305dc70ae8d427970c930e44ce51166ee22eae2c3df32338314589f15fb9c85" } } ], "extra": [ 1, 174, 77, 41, 184, 79, 22, 86, 174, 174, 120, 31, 13, 18, 199, 251, 212, 207, 18, 84, 15, 208, 23, 46, 44, 167, 152, 214, 176, 154, 32, 232, 5, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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