Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd9e874f90807424ce31fb157db772ef50b9a0857d1b47ac8db4c9d8dcda70c3

Tx prefix hash: a1333a1d324c3a70a421b0b87bfbd7be0ee435a09a3119c58d1c81e1cedccdfd
Tx public key: bb309e3d6570e7955819e30fd24b2a5c0fe43111e609f0551ca590c3ef74cb44
Timestamp: 1696071657 Timestamp [UCT]: 2023-09-30 11:00:57 Age [y:d:h:m:s]: 01:186:21:16:37
Block: 859387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394612 RingCT/type: yes/0
Extra: 01bb309e3d6570e7955819e30fd24b2a5c0fe43111e609f0551ca590c3ef74cb44021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.871955183000 dcy

stealth address amount amount idx
00: 4dc79043be23337743efe27fa7d6dd611d039f86f35d1a4a0fe7b523c0727e5c 0.871955183000 1313611 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": 859397, "vin": [ { "gen": { "height": 859387 } } ], "vout": [ { "amount": 871955183, "target": { "key": "4dc79043be23337743efe27fa7d6dd611d039f86f35d1a4a0fe7b523c0727e5c" } } ], "extra": [ 1, 187, 48, 158, 61, 101, 112, 231, 149, 88, 25, 227, 15, 210, 75, 42, 92, 15, 228, 49, 17, 230, 9, 240, 85, 28, 165, 144, 195, 239, 116, 203, 68, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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