Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c1101925aa6da33b097d1208e84fb15247194a1353a501d4b99c7a2a20d80ee

Tx prefix hash: 8fad562da3ee6f6e9f37038df2dc29b26985f24ade59a7b0f0fd9cd6f92f1673
Tx public key: f6ec88065263e36827c3dabcb867cee773a0926265e7157644161eb9408f7e95
Timestamp: 1697109513 Timestamp [UCT]: 2023-10-12 11:18:33 Age [y:d:h:m:s]: 02:020:08:52:59
Block: 867996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534165 RingCT/type: yes/0
Extra: 01f6ec88065263e36827c3dabcb867cee773a0926265e7157644161eb9408f7e9502110000000433af99f4000000000000000000

1 output(s) for total of 0.816524010000 dcy

stealth address amount amount idx
00: 7eb3a4de53ea5ef64e57c9411cc2837e7daab406b84e9148b87cf8c8d9e4c2b3 0.816524010000 1322741 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": 868006, "vin": [ { "gen": { "height": 867996 } } ], "vout": [ { "amount": 816524010, "target": { "key": "7eb3a4de53ea5ef64e57c9411cc2837e7daab406b84e9148b87cf8c8d9e4c2b3" } } ], "extra": [ 1, 246, 236, 136, 6, 82, 99, 227, 104, 39, 195, 218, 188, 184, 103, 206, 231, 115, 160, 146, 98, 101, 231, 21, 118, 68, 22, 30, 185, 64, 143, 126, 149, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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