Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b8c099036bfebb36857bc23ce85c44acac8746f9de9bc52b1d8219a74b94371

Tx prefix hash: 9b99e8c538042f312eb5acf654c84800b3c6d85e0b40809c244a07c82c75b13e
Tx public key: 0235e5c32a557bf22d86effd14f4caccb2ad0995aef4af8ab872beed8c654624
Timestamp: 1705060570 Timestamp [UCT]: 2024-01-12 11:56:10 Age [y:d:h:m:s]: 01:074:00:36:30
Block: 933687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313991 RingCT/type: yes/0
Extra: 010235e5c32a557bf22d86effd14f4caccb2ad0995aef4af8ab872beed8c6546240211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a217a46a73bce6926930458aa46f27d8fcfeb602fa8c36a543e61fdcdc1c0e56 0.600000000000 1391657 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": 933697, "vin": [ { "gen": { "height": 933687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a217a46a73bce6926930458aa46f27d8fcfeb602fa8c36a543e61fdcdc1c0e56" } } ], "extra": [ 1, 2, 53, 229, 195, 42, 85, 123, 242, 45, 134, 239, 253, 20, 244, 202, 204, 178, 173, 9, 149, 174, 244, 175, 138, 184, 114, 190, 237, 140, 101, 70, 36, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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