Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c3b4a18c512c7de5d8bf7391a4a131971620f703af77ede9ee696af4a545af

Tx prefix hash: b8d6d27c6637b53f4db1ee9a5b3b1f12638378a5f589dd82efc977c66adc458f
Tx public key: 2f9bf4b41ae5e7d4300bda3dd9f63bc36020cd00e2dcec65f2ca727f6ed25dc2
Timestamp: 1693997606 Timestamp [UCT]: 2023-09-06 10:53:26 Age [y:d:h:m:s]: 01:217:15:05:41
Block: 842164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416652 RingCT/type: yes/0
Extra: 012f9bf4b41ae5e7d4300bda3dd9f63bc36020cd00e2dcec65f2ca727f6ed25dc2021100000003faf35c9c000000000000000000

1 output(s) for total of 0.994400049000 dcy

stealth address amount amount idx
00: f936016332bd425a2f087416b68fb617d51cfd3376019cdfedd76ea8df826085 0.994400049000 1295258 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": 842174, "vin": [ { "gen": { "height": 842164 } } ], "vout": [ { "amount": 994400049, "target": { "key": "f936016332bd425a2f087416b68fb617d51cfd3376019cdfedd76ea8df826085" } } ], "extra": [ 1, 47, 155, 244, 180, 26, 229, 231, 212, 48, 11, 218, 61, 217, 246, 59, 195, 96, 32, 205, 0, 226, 220, 236, 101, 242, 202, 114, 127, 110, 210, 93, 194, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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