Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e6eae4be76c01f63ae75dbeb2d852515ce7ba83810a79ca5cd2010a6eb9b606

Tx prefix hash: 17bad1beb01b5a79e6987faf85db8529cdbc0f31062a0c9e3764eb94b953b232
Tx public key: dfcdd639980fd3c2e52c3b93aa2190fb0337a7263a20980c2d4c3952bbfaac27
Timestamp: 1707198896 Timestamp [UCT]: 2024-02-06 05:54:56 Age [y:d:h:m:s]: 01:022:12:53:58
Block: 951418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277130 RingCT/type: yes/0
Extra: 01dfcdd639980fd3c2e52c3b93aa2190fb0337a7263a20980c2d4c3952bbfaac2702110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78176f7d14c4769d30914ac1e50b8b6cfdbab11e55fb01fb7b04268a177665f2 0.600000000000 1410180 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": 951428, "vin": [ { "gen": { "height": 951418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78176f7d14c4769d30914ac1e50b8b6cfdbab11e55fb01fb7b04268a177665f2" } } ], "extra": [ 1, 223, 205, 214, 57, 152, 15, 211, 194, 229, 44, 59, 147, 170, 33, 144, 251, 3, 55, 167, 38, 58, 32, 152, 12, 45, 76, 57, 82, 187, 250, 172, 39, 2, 17, 0, 0, 0, 12, 89, 218, 211, 245, 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