Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b77310f4faa9ff2542cf239c30d86c5a3cf75c3103565d6c1731472a305b4c6

Tx prefix hash: e2f9f351f041deaedfdf06cf95004447b2a080c5ebf1bc5159dae7d384517680
Tx public key: ca2df988bde810e70c9b4a9bcd7123fa2e8e44eefde72370f98bfb2aa3efa158
Timestamp: 1725201927 Timestamp [UCT]: 2024-09-01 14:45:27 Age [y:d:h:m:s]: 00:270:02:43:20
Block: 1100689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192938 RingCT/type: yes/0
Extra: 01ca2df988bde810e70c9b4a9bcd7123fa2e8e44eefde72370f98bfb2aa3efa15802110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2cf87b6a4ecfd3c3293575f0be9fe07eaf183ce12821faa88e379feaa1cadbf 0.600000000000 1576668 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": 1100699, "vin": [ { "gen": { "height": 1100689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2cf87b6a4ecfd3c3293575f0be9fe07eaf183ce12821faa88e379feaa1cadbf" } } ], "extra": [ 1, 202, 45, 249, 136, 189, 232, 16, 231, 12, 155, 74, 155, 205, 113, 35, 250, 46, 142, 68, 238, 253, 231, 35, 112, 249, 139, 251, 42, 163, 239, 161, 88, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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