Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf08720d4d42a5bc75ec1184bd088ef24e22c877e21b949872daa5c2168d61a

Tx prefix hash: 678ab77be1b76b1d13c8cc6cc69a45dc890dc57877f3db856761aeb0f1a60971
Tx public key: 89f2d55014b13ca3f956f5d3dae884bd7a1e65d4472c147e63c53148b5e285f3
Timestamp: 1730629669 Timestamp [UCT]: 2024-11-03 10:27:49 Age [y:d:h:m:s]: 00:149:10:58:51
Block: 1145602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106626 RingCT/type: yes/0
Extra: 0189f2d55014b13ca3f956f5d3dae884bd7a1e65d4472c147e63c53148b5e285f30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28363014083e2b8aa0cacb8096e1007bf89dfd6d6d77c3199a22c9960dee7dd4 0.600000000000 1630077 of 15

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": 1145612, "vin": [ { "gen": { "height": 1145602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28363014083e2b8aa0cacb8096e1007bf89dfd6d6d77c3199a22c9960dee7dd4" } } ], "extra": [ 1, 137, 242, 213, 80, 20, 177, 60, 163, 249, 86, 245, 211, 218, 232, 132, 189, 122, 30, 101, 212, 71, 44, 20, 126, 99, 197, 49, 72, 181, 226, 133, 243, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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