Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7420cf831c2520b7943c4da7fa5210acabc32edcab4b35b4e3c4c12aeb52af6d

Tx prefix hash: a67bc2658b6db36222ceb6f14fd1ac0b3b22685cdd55d264fdc3e6566549d2df
Tx public key: ec9fb79c3ad9497ec0e002f438d93fc803006ca096d6dfe8f207214495c0ddfd
Timestamp: 1717613776 Timestamp [UCT]: 2024-06-05 18:56:16 Age [y:d:h:m:s]: 00:317:08:19:24
Block: 1037765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226808 RingCT/type: yes/0
Extra: 01ec9fb79c3ad9497ec0e002f438d93fc803006ca096d6dfe8f207214495c0ddfd02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa1a4ee04b7dab06862b73ddbc230a71bebe412f2ad930a267a9ea6aaec0f506 0.600000000000 1506320 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": 1037775, "vin": [ { "gen": { "height": 1037765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa1a4ee04b7dab06862b73ddbc230a71bebe412f2ad930a267a9ea6aaec0f506" } } ], "extra": [ 1, 236, 159, 183, 156, 58, 217, 73, 126, 192, 224, 2, 244, 56, 217, 63, 200, 3, 0, 108, 160, 150, 214, 223, 232, 242, 7, 33, 68, 149, 192, 221, 253, 2, 17, 0, 0, 0, 2, 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