Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e4f8663acd5fb056f2573f26470133d4a499fcd761706e2c98d2aec22dec66

Tx prefix hash: b6efe347f3e9cbdc9d6fc1cfaa938fd6fe0fcdf4526fee352874617da55d8980
Tx public key: 8b117cf4a429ae08877bad31f05bfa68461327d2f997cace8bf0de46608413d6
Timestamp: 1638081286 Timestamp [UCT]: 2021-11-28 06:34:46 Age [y:d:h:m:s]: 03:106:18:25:59
Block: 383779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 855000 RingCT/type: yes/0
Extra: 018b117cf4a429ae08877bad31f05bfa68461327d2f997cace8bf0de46608413d602110000000fb494d89c000000000000000000

1 output(s) for total of 32.838912936000 dcy

stealth address amount amount idx
00: 0b18bf3ac644b9a5c0ddd607c1e4124137d41b05492912d857e1d62f21cfe55f 32.838912936000 774758 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": 383789, "vin": [ { "gen": { "height": 383779 } } ], "vout": [ { "amount": 32838912936, "target": { "key": "0b18bf3ac644b9a5c0ddd607c1e4124137d41b05492912d857e1d62f21cfe55f" } } ], "extra": [ 1, 139, 17, 124, 244, 164, 41, 174, 8, 135, 123, 173, 49, 240, 91, 250, 104, 70, 19, 39, 210, 249, 151, 202, 206, 139, 240, 222, 70, 96, 132, 19, 214, 2, 17, 0, 0, 0, 15, 180, 148, 216, 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