Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4be4150bccbf1dca36de0649370901c067bebf2347567fa66bf1ae438307aa61

Tx prefix hash: 0e44c94206abf2123ae31e060f43ea494aa6dc7359fac70265669504b443d4af
Tx public key: 817c9344b454a9c6c6fa2a7c44e49fe25a8520b094a52ae6e833a3b447d1aa8f
Timestamp: 1625345483 Timestamp [UCT]: 2021-07-03 20:51:23 Age [y:d:h:m:s]: 03:126:04:57:10
Block: 287833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 859645 RingCT/type: yes/0
Extra: 01817c9344b454a9c6c6fa2a7c44e49fe25a8520b094a52ae6e833a3b447d1aa8f021100000029bffe00bb000000000000000000

1 output(s) for total of 68.279493994000 dcy

stealth address amount amount idx
00: aa178adca9d9e7b2d1b9e1220c3b5362edef10a0fca47241ab8bac923b3a6af7 68.279493994000 603087 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": 287843, "vin": [ { "gen": { "height": 287833 } } ], "vout": [ { "amount": 68279493994, "target": { "key": "aa178adca9d9e7b2d1b9e1220c3b5362edef10a0fca47241ab8bac923b3a6af7" } } ], "extra": [ 1, 129, 124, 147, 68, 180, 84, 169, 198, 198, 250, 42, 124, 68, 228, 159, 226, 90, 133, 32, 176, 148, 165, 42, 230, 232, 51, 163, 180, 71, 209, 170, 143, 2, 17, 0, 0, 0, 41, 191, 254, 0, 187, 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