Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ceddbac60b84f26cd80bf92fd127a07404ebdb2299f600ebffaba67c8e5b5e4

Tx prefix hash: 588f94e95cb7864993e5522fe111f73b655a91ae812f9fd9dd531a6e6e15e457
Tx public key: 0950751f4433e367f287e9bc8c2fd31d97d50db292e7d609daed8d542d9788ea
Timestamp: 1712948434 Timestamp [UCT]: 2024-04-12 19:00:34 Age [y:d:h:m:s]: 01:065:04:03:57
Block: 999069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307481 RingCT/type: yes/0
Extra: 010950751f4433e367f287e9bc8c2fd31d97d50db292e7d609daed8d542d9788ea02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ae654f448664dab14f6099041d6912594f01d684a1483af3c63c26b09f461c1 0.600000000000 1459545 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": 999079, "vin": [ { "gen": { "height": 999069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ae654f448664dab14f6099041d6912594f01d684a1483af3c63c26b09f461c1" } } ], "extra": [ 1, 9, 80, 117, 31, 68, 51, 227, 103, 242, 135, 233, 188, 140, 47, 211, 29, 151, 213, 13, 178, 146, 231, 214, 9, 218, 237, 141, 84, 45, 151, 136, 234, 2, 17, 0, 0, 0, 14, 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