Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baa207bcd5d750575d46d53a9b8d310995b5accc0e2f9aa667c76b8fac4d279e

Tx prefix hash: ecfbef39fc2ea2d106d32b8d835dce609e950e62b483c27b03790c718c2a7d63
Tx public key: d6a9795fc437b45714a810232c364321fdc51cbbb0f247af651864c9efb259f9
Timestamp: 1717275997 Timestamp [UCT]: 2024-06-01 21:06:37 Age [y:d:h:m:s]: 00:151:18:23:09
Block: 1034986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108616 RingCT/type: yes/0
Extra: 01d6a9795fc437b45714a810232c364321fdc51cbbb0f247af651864c9efb259f9021100000004e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dde1188d9f20e14400583d12c75d4642c4533dba26a30730d8b7e6c2250da30 0.600000000000 1503505 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": 1034996, "vin": [ { "gen": { "height": 1034986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dde1188d9f20e14400583d12c75d4642c4533dba26a30730d8b7e6c2250da30" } } ], "extra": [ 1, 214, 169, 121, 95, 196, 55, 180, 87, 20, 168, 16, 35, 44, 54, 67, 33, 253, 197, 28, 187, 176, 242, 71, 175, 101, 24, 100, 201, 239, 178, 89, 249, 2, 17, 0, 0, 0, 4, 224, 133, 50, 182, 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