Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 976283f215b5946b4874d812155537dc829b1622fc976b6d67f4cac7b4a076de

Tx prefix hash: 7f35b2d8bebc641355a9d8755f815f4a2584af34ddfc8c97a3b374b8b561373b
Tx public key: c27c4caa99467e65faba18ea67c498a301bb3973deb4d824cc373c1ee87043b1
Timestamp: 1723794735 Timestamp [UCT]: 2024-08-16 07:52:15 Age [y:d:h:m:s]: 00:254:05:00:16
Block: 1089014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181579 RingCT/type: yes/0
Extra: 01c27c4caa99467e65faba18ea67c498a301bb3973deb4d824cc373c1ee87043b1021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 793d1a9a097b1a06af693f1be2d8ccde025bf1a9e0e4d13fc5304df912010545 0.600000000000 1563633 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": 1089024, "vin": [ { "gen": { "height": 1089014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "793d1a9a097b1a06af693f1be2d8ccde025bf1a9e0e4d13fc5304df912010545" } } ], "extra": [ 1, 194, 124, 76, 170, 153, 70, 126, 101, 250, 186, 24, 234, 103, 196, 152, 163, 1, 187, 57, 115, 222, 180, 216, 36, 204, 55, 60, 30, 232, 112, 67, 177, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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