Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da8da15c4816fef917ffeb307be7ac1c110a1bd1aa50764fc3d95e8b80096058

Tx prefix hash: e73b7a3fa04b6d636763e3b4260f0fc83a31fdd991294b807776650fc8657fee
Tx public key: c84f3707b6cbf13c34016dc9e65f1a1b600756a9a5a64772affcdd317f5526f9
Timestamp: 1718776458 Timestamp [UCT]: 2024-06-19 05:54:18 Age [y:d:h:m:s]: 00:291:10:32:28
Block: 1047418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208246 RingCT/type: yes/0
Extra: 01c84f3707b6cbf13c34016dc9e65f1a1b600756a9a5a64772affcdd317f5526f90211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 304c1e56887e0919a78861216f514cb06fc6228324a45fd63d049dba8da24c0a 0.600000000000 1517239 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": 1047428, "vin": [ { "gen": { "height": 1047418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "304c1e56887e0919a78861216f514cb06fc6228324a45fd63d049dba8da24c0a" } } ], "extra": [ 1, 200, 79, 55, 7, 182, 203, 241, 60, 52, 1, 109, 201, 230, 95, 26, 27, 96, 7, 86, 169, 165, 166, 71, 114, 175, 252, 221, 49, 127, 85, 38, 249, 2, 17, 0, 0, 0, 8, 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