Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f1a47e5b77c7158c4d560ffafb39672a2d7288991711e5eb48dc190230ebab

Tx prefix hash: 3f832844395bed16da8256fb337d9a13e4d34b9131bffd93276c1a2c22b262e9
Tx public key: 4a95e8f1aeb4d60d2dfa63bff29194a132ddcc67b32ddf81a5afe15ff49a5e08
Timestamp: 1705300633 Timestamp [UCT]: 2024-01-15 06:37:13 Age [y:d:h:m:s]: 01:091:06:32:20
Block: 935662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326343 RingCT/type: yes/0
Extra: 014a95e8f1aeb4d60d2dfa63bff29194a132ddcc67b32ddf81a5afe15ff49a5e0802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85dedb560019fcb9be62a28d62e4c30f75cbb30d06e2c89df374916eb477234f 0.600000000000 1393678 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": 935672, "vin": [ { "gen": { "height": 935662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85dedb560019fcb9be62a28d62e4c30f75cbb30d06e2c89df374916eb477234f" } } ], "extra": [ 1, 74, 149, 232, 241, 174, 180, 214, 13, 45, 250, 99, 191, 242, 145, 148, 161, 50, 221, 204, 103, 179, 45, 223, 129, 165, 175, 225, 95, 244, 154, 94, 8, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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