Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a647cb089e2673f46c4a7cda50ca3208a94aa0f72f8ae1a09e5723696a67e3b

Tx prefix hash: f49bb595eb9fd17b5f2c4a7d1fcdf9140a4cf958b7ec0307119f42ff592ac3da
Tx public key: 597f95d4086495a102bed02ace79e85b8f604b27913bc8eac00e1d3d2512eaef
Timestamp: 1730389346 Timestamp [UCT]: 2024-10-31 15:42:26 Age [y:d:h:m:s]: 00:082:21:24:21
Block: 1143606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59270 RingCT/type: yes/0
Extra: 01597f95d4086495a102bed02ace79e85b8f604b27913bc8eac00e1d3d2512eaef021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fb2295c322c09d79200624aae966a0db144482e244f5a5b0821aa0bb23c1447 0.600000000000 1627535 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": 1143616, "vin": [ { "gen": { "height": 1143606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fb2295c322c09d79200624aae966a0db144482e244f5a5b0821aa0bb23c1447" } } ], "extra": [ 1, 89, 127, 149, 212, 8, 100, 149, 161, 2, 190, 208, 42, 206, 121, 232, 91, 143, 96, 75, 39, 145, 59, 200, 234, 192, 14, 29, 61, 37, 18, 234, 239, 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