Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1b69c2bbb6a59bd62f8d04b3cd2b542fb4b68df010e5cd448dd6548e7bbbcd3

Tx prefix hash: 3d4f72148dd4b9aa09cf25e765a15f6f2472e006b5049df876ff04640add1a82
Tx public key: e70f18cd9d8e8ff8dcb45a8230a8e63cad31a5c4bad21a1f91f1fb38d310dfc0
Timestamp: 1702896904 Timestamp [UCT]: 2023-12-18 10:55:04 Age [y:d:h:m:s]: 01:129:15:13:00
Block: 915760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353780 RingCT/type: yes/0
Extra: 01e70f18cd9d8e8ff8dcb45a8230a8e63cad31a5c4bad21a1f91f1fb38d310dfc002110000000f75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8c407693a8894e31d7b784a62dcd102a1200b976c335f946af5c0056463a089 0.600000000000 1373184 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": 915770, "vin": [ { "gen": { "height": 915760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8c407693a8894e31d7b784a62dcd102a1200b976c335f946af5c0056463a089" } } ], "extra": [ 1, 231, 15, 24, 205, 157, 142, 143, 248, 220, 180, 90, 130, 48, 168, 230, 60, 173, 49, 165, 196, 186, 210, 26, 31, 145, 241, 251, 56, 211, 16, 223, 192, 2, 17, 0, 0, 0, 15, 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