Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6f6fb2e7b331d15ca603b9604ae21326eb5d71d0ae44ca8e7ec6eabfb93426

Tx prefix hash: 27d6e85408fbb5d6e1f705a902dd1e39d5babb1cc7a3274c7fd355be4653ceee
Tx public key: ed07094db6d5213188b9aadddd89128214cfb057e17bc95a0fbf4c6f948e7395
Timestamp: 1647430843 Timestamp [UCT]: 2022-03-16 11:40:43 Age [y:d:h:m:s]: 02:363:22:11:22
Block: 459648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 779397 RingCT/type: yes/0
Extra: 01ed07094db6d5213188b9aadddd89128214cfb057e17bc95a0fbf4c6f948e739502110000000b5eb576c5000000000000000000

1 output(s) for total of 18.407534863000 dcy

stealth address amount amount idx
00: 6ae04f945d6a77eb613ec33c1ead549542a87b2a2ce50f8dabe7b38795f7d08c 18.407534863000 876439 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": 459658, "vin": [ { "gen": { "height": 459648 } } ], "vout": [ { "amount": 18407534863, "target": { "key": "6ae04f945d6a77eb613ec33c1ead549542a87b2a2ce50f8dabe7b38795f7d08c" } } ], "extra": [ 1, 237, 7, 9, 77, 182, 213, 33, 49, 136, 185, 170, 221, 221, 137, 18, 130, 20, 207, 176, 87, 225, 123, 201, 90, 15, 191, 76, 111, 148, 142, 115, 149, 2, 17, 0, 0, 0, 11, 94, 181, 118, 197, 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