Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cef2fee61e6035be93c9f333222419820b1fdffcae7aef040a9354b48ed61e68

Tx prefix hash: 5d5929c8f065c7e7d1d720d055479386d8459c44dbdddbd1b5500acc3e3d44b0
Tx public key: 8314d6a668ba4a07b239394987fdb85afa0a2cdc58e0329d0a3f8370d25741ca
Timestamp: 1704062748 Timestamp [UCT]: 2023-12-31 22:45:48 Age [y:d:h:m:s]: 01:128:17:45:25
Block: 925413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353141 RingCT/type: yes/0
Extra: 018314d6a668ba4a07b239394987fdb85afa0a2cdc58e0329d0a3f8370d25741ca0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ede5e537549fefa6ea94709525195a7c0615a83d1f340dfe193bb6cc9160b52f 0.600000000000 1383175 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": 925423, "vin": [ { "gen": { "height": 925413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ede5e537549fefa6ea94709525195a7c0615a83d1f340dfe193bb6cc9160b52f" } } ], "extra": [ 1, 131, 20, 214, 166, 104, 186, 74, 7, 178, 57, 57, 73, 135, 253, 184, 90, 250, 10, 44, 220, 88, 224, 50, 157, 10, 63, 131, 112, 210, 87, 65, 202, 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