Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ed723b9dc61bbf35cde2c8b3b7b11f34f09d9485e8ecf08fd0f25fad9288c79

Tx prefix hash: d6b0560b0b595e0ecd85d711f6b347b44ee328f22ea57118bd7df32fc6c35e24
Tx public key: e93125db1cb6b8874ca1077c182d13afc53ed696708265088ce44710bc14989f
Timestamp: 1708854098 Timestamp [UCT]: 2024-02-25 09:41:38 Age [y:d:h:m:s]: 01:035:14:45:35
Block: 965160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286462 RingCT/type: yes/0
Extra: 01e93125db1cb6b8874ca1077c182d13afc53ed696708265088ce44710bc14989f0211000000187a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb76928c76480a8f7c47d874d546853451b51aac3c2bdb60abe78e99279ca40e 0.600000000000 1424909 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": 965170, "vin": [ { "gen": { "height": 965160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb76928c76480a8f7c47d874d546853451b51aac3c2bdb60abe78e99279ca40e" } } ], "extra": [ 1, 233, 49, 37, 219, 28, 182, 184, 135, 76, 161, 7, 124, 24, 45, 19, 175, 197, 62, 214, 150, 112, 130, 101, 8, 140, 228, 71, 16, 188, 20, 152, 159, 2, 17, 0, 0, 0, 24, 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