Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fac2065a07b551b32c8d13a8d892fa7ab31594c6297fe221aa07d436a8399f9

Tx prefix hash: 0100e346d8f59a919f5c7d8d122be0c8557e46579bf9f689b181abb156d3ccf5
Tx public key: 40c1a05260048ee5e54893afad0f26098a6dcab9d1608d73a96a25f02fdb4c37
Timestamp: 1674400317 Timestamp [UCT]: 2023-01-22 15:11:57 Age [y:d:h:m:s]: 02:146:16:39:56
Block: 680386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 626421 RingCT/type: yes/0
Extra: 0140c1a05260048ee5e54893afad0f26098a6dcab9d1608d73a96a25f02fdb4c3702110000000333af99f4000000000000000000

1 output(s) for total of 3.416635762000 dcy

stealth address amount amount idx
00: 622d0b01307085996366867c40515a42d4d82c320039268b8ccc5ba2c37262b5 3.416635762000 1122421 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": 680396, "vin": [ { "gen": { "height": 680386 } } ], "vout": [ { "amount": 3416635762, "target": { "key": "622d0b01307085996366867c40515a42d4d82c320039268b8ccc5ba2c37262b5" } } ], "extra": [ 1, 64, 193, 160, 82, 96, 4, 142, 229, 229, 72, 147, 175, 173, 15, 38, 9, 138, 109, 202, 185, 209, 96, 141, 115, 169, 106, 37, 240, 47, 219, 76, 55, 2, 17, 0, 0, 0, 3, 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