Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab619ce99bf590f9ef8894980d2123318ba71b94bb928f6b1cdc18067b0b2bd0

Tx prefix hash: 4168eed405f3a260f85b93f7fba1e6e4d8402d231263e7639aaa82eaec9ba81a
Tx public key: cfe8ba5b80fa77c26c8b7067455bb501dfad04cc7dbcee4d31f6e90ffdca6d66
Timestamp: 1724653969 Timestamp [UCT]: 2024-08-26 06:32:49 Age [y:d:h:m:s]: 00:219:12:31:26
Block: 1096124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156764 RingCT/type: yes/0
Extra: 01cfe8ba5b80fa77c26c8b7067455bb501dfad04cc7dbcee4d31f6e90ffdca6d6602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23c2a45b6ac4eb06540d96b100cc585cba2478a6bc2499c359b62ce8c632e063 0.600000000000 1571311 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": 1096134, "vin": [ { "gen": { "height": 1096124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23c2a45b6ac4eb06540d96b100cc585cba2478a6bc2499c359b62ce8c632e063" } } ], "extra": [ 1, 207, 232, 186, 91, 128, 250, 119, 194, 108, 139, 112, 103, 69, 91, 181, 1, 223, 173, 4, 204, 125, 188, 238, 77, 49, 246, 233, 15, 253, 202, 109, 102, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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