Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5085d6940e3d571aba0fee624f5ff33d2143bbf8933c4cc342662701aa7018f7

Tx prefix hash: a16ccaab2662843416e1233d44d0ffd705eb7fc0a73e1dd485db74ea0bab64dd
Tx public key: f1657128df6bbe5cccd3ea2a8d5a32d616099d881d95dd95dd9d82ce9b81095a
Timestamp: 1637433093 Timestamp [UCT]: 2021-11-20 18:31:33 Age [y:d:h:m:s]: 02:351:04:47:27
Block: 378446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 768948 RingCT/type: yes/0
Extra: 01f1657128df6bbe5cccd3ea2a8d5a32d616099d881d95dd95dd9d82ce9b81095a02110000000196e5bff5000000000000000000

1 output(s) for total of 34.202014329000 dcy

stealth address amount amount idx
00: d4be21246724da87c6575a7f3165b26d55469d6e40313b3c9d21e217873e4bf7 34.202014329000 765288 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": 378456, "vin": [ { "gen": { "height": 378446 } } ], "vout": [ { "amount": 34202014329, "target": { "key": "d4be21246724da87c6575a7f3165b26d55469d6e40313b3c9d21e217873e4bf7" } } ], "extra": [ 1, 241, 101, 113, 40, 223, 107, 190, 92, 204, 211, 234, 42, 141, 90, 50, 214, 22, 9, 157, 136, 29, 149, 221, 149, 221, 157, 130, 206, 155, 129, 9, 90, 2, 17, 0, 0, 0, 1, 150, 229, 191, 245, 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