Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 697884762096e94d4a58ee0927546c6aebd62fcccfe6599ce3818b17551789fb

Tx prefix hash: bb5ad42b67d689c6ceba5ad40b2802b0932ce21f3683af7ca83a83ef75997b09
Tx public key: 5d297e8fbb0289e9030ba5a7b748abd75f8a35475c2a378d514be50b0c3a4b86
Timestamp: 1735711599 Timestamp [UCT]: 2025-01-01 06:06:39 Age [y:d:h:m:s]: 00:164:00:47:30
Block: 1187676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116994 RingCT/type: yes/0
Extra: 015d297e8fbb0289e9030ba5a7b748abd75f8a35475c2a378d514be50b0c3a4b86021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6a11c8ec52f7bee364600433d966f7a9f1c444ca4f4c6515e35ca55488f6b27 0.600000000000 1674169 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": 1187686, "vin": [ { "gen": { "height": 1187676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6a11c8ec52f7bee364600433d966f7a9f1c444ca4f4c6515e35ca55488f6b27" } } ], "extra": [ 1, 93, 41, 126, 143, 187, 2, 137, 233, 3, 11, 165, 167, 183, 72, 171, 215, 95, 138, 53, 71, 92, 42, 55, 141, 81, 75, 229, 11, 12, 58, 75, 134, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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