Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8fc4efb211009eee2f72606347785fc526165094a1cdc95cbb27d998a66920

Tx prefix hash: 1c4121974c80f7ad3ebbba78f40386bd2995bf1abfd9e00e9277c3a4677e0d33
Tx public key: 8c1a28a8ab9b1f4522177c27f8a52495ee1f9d1b91fc8cbf7ec8bf0108ef9c13
Timestamp: 1584760944 Timestamp [UCT]: 2020-03-21 03:22:24 Age [y:d:h:m:s]: 04:349:09:50:40
Block: 86066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145912 RingCT/type: yes/0
Extra: 018c1a28a8ab9b1f4522177c27f8a52495ee1f9d1b91fc8cbf7ec8bf0108ef9c13021100000007c2c2f844000000000000000000

1 output(s) for total of 318.293958468000 dcy

stealth address amount amount idx
00: 71b6908cfc5a9e0a295832b2fb9987bd0e9aafd79d586c0d3c1af3156a284d52 318.293958468000 155334 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": 86076, "vin": [ { "gen": { "height": 86066 } } ], "vout": [ { "amount": 318293958468, "target": { "key": "71b6908cfc5a9e0a295832b2fb9987bd0e9aafd79d586c0d3c1af3156a284d52" } } ], "extra": [ 1, 140, 26, 40, 168, 171, 155, 31, 69, 34, 23, 124, 39, 248, 165, 36, 149, 238, 31, 157, 27, 145, 252, 140, 191, 126, 200, 191, 1, 8, 239, 156, 19, 2, 17, 0, 0, 0, 7, 194, 194, 248, 68, 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