Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac736557d51162c99eacde1fc04af61fa2431542899a855e6ae5a710d926ebe0

Tx prefix hash: 191dd4e60b77b5e31b63e272601ee966b4c3c1fe37e7c41991cb042e733550d0
Tx public key: 7ec73cf053caa77f193de76ac73e30d726f66e751d70eb6a9e721583623f6389
Timestamp: 1716835007 Timestamp [UCT]: 2024-05-27 18:36:47 Age [y:d:h:m:s]: 00:301:04:37:45
Block: 1031331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215238 RingCT/type: yes/0
Extra: 017ec73cf053caa77f193de76ac73e30d726f66e751d70eb6a9e721583623f638902110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1e988fb8fe563f6439e45ee2fc7c91e9fae0ef3dbfb163b4a9c017dfae8db56 0.600000000000 1499756 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": 1031341, "vin": [ { "gen": { "height": 1031331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1e988fb8fe563f6439e45ee2fc7c91e9fae0ef3dbfb163b4a9c017dfae8db56" } } ], "extra": [ 1, 126, 199, 60, 240, 83, 202, 167, 127, 25, 61, 231, 106, 199, 62, 48, 215, 38, 246, 110, 117, 29, 112, 235, 106, 158, 114, 21, 131, 98, 63, 99, 137, 2, 17, 0, 0, 0, 6, 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