Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32d5b62f945811ab8c112c9a84772a848848588c2c09fc1aa525657b92f95176

Tx prefix hash: f2782447c0df2ec1f5eceb8f1e8826ee7120b31739fbeff8b80b5353e10e20af
Tx public key: eb22da8c488e5817b6a2a6e6ad60439a2d49731d7dd4b1a539541f59af5be08c
Timestamp: 1700917597 Timestamp [UCT]: 2023-11-25 13:06:37 Age [y:d:h:m:s]: 01:112:22:10:22
Block: 899361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341880 RingCT/type: yes/0
Extra: 01eb22da8c488e5817b6a2a6e6ad60439a2d49731d7dd4b1a539541f59af5be08c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.642752314000 dcy

stealth address amount amount idx
00: 2988bcdf6e81042911b943c1dbfb47c8f14989e5735e0cd35df482a404bfcf9a 0.642752314000 1355814 of 0

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": 899371, "vin": [ { "gen": { "height": 899361 } } ], "vout": [ { "amount": 642752314, "target": { "key": "2988bcdf6e81042911b943c1dbfb47c8f14989e5735e0cd35df482a404bfcf9a" } } ], "extra": [ 1, 235, 34, 218, 140, 72, 142, 88, 23, 182, 162, 166, 230, 173, 96, 67, 154, 45, 73, 115, 29, 125, 212, 177, 165, 57, 84, 31, 89, 175, 91, 224, 140, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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