Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58fc0db1b2ccf3cfb449becb679eb6824415d0044cdecc2dae79b420209b5619

Tx prefix hash: 0ca8540066ed0ca41e87c70e4492593c9c13b3ff7005c0c0f61f41c18f9b6fed
Tx public key: 7f40e6a1a674e9a469f4226bbfbdba2b28e62464a5971fdcf3b4da27b66a780e
Timestamp: 1695488950 Timestamp [UCT]: 2023-09-23 17:09:10 Age [y:d:h:m:s]: 01:197:13:21:31
Block: 854543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402251 RingCT/type: yes/0
Extra: 017f40e6a1a674e9a469f4226bbfbdba2b28e62464a5971fdcf3b4da27b66a780e021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.904782836000 dcy

stealth address amount amount idx
00: ea26c04a5e7f469ae1eba2d76e6ee26ababf9bc5cbb6ab85883abcfb38f5a5ea 0.904782836000 1308523 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": 854553, "vin": [ { "gen": { "height": 854543 } } ], "vout": [ { "amount": 904782836, "target": { "key": "ea26c04a5e7f469ae1eba2d76e6ee26ababf9bc5cbb6ab85883abcfb38f5a5ea" } } ], "extra": [ 1, 127, 64, 230, 161, 166, 116, 233, 164, 105, 244, 34, 107, 191, 189, 186, 43, 40, 230, 36, 100, 165, 151, 31, 220, 243, 180, 218, 39, 182, 106, 120, 14, 2, 17, 0, 0, 0, 4, 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