Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2feb5410f80e1fb3aeff5e9cd85cb3af574597157ce3b344a666556dd806851

Tx prefix hash: 4791bf53f495956127249ceee09c81fae77017b1cf7449de243a50b0a2453558
Tx public key: 4c924ce1db46cbcaee1e9a097d85d98600bf43e785a9dab475a13ae85b05f654
Timestamp: 1718815861 Timestamp [UCT]: 2024-06-19 16:51:01 Age [y:d:h:m:s]: 00:295:06:11:28
Block: 1047736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210990 RingCT/type: yes/0
Extra: 014c924ce1db46cbcaee1e9a097d85d98600bf43e785a9dab475a13ae85b05f6540211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c91c7a11447d30350686c067c61980ea02e61c80b3b6d3e2f78cd4f51a1d8e0 0.600000000000 1517639 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": 1047746, "vin": [ { "gen": { "height": 1047736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c91c7a11447d30350686c067c61980ea02e61c80b3b6d3e2f78cd4f51a1d8e0" } } ], "extra": [ 1, 76, 146, 76, 225, 219, 70, 203, 202, 238, 30, 154, 9, 125, 133, 217, 134, 0, 191, 67, 231, 133, 169, 218, 180, 117, 161, 58, 232, 91, 5, 246, 84, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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