Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0e5ea3bf53440d5c0d1992d658479e2d043d0872692bf4289b7d2ebbc031eb

Tx prefix hash: 9516ad17a8293e1e8167c8171214d50fc9ca20f1e38d07dfd0da912a80bde2dc
Tx public key: 1c5f8de5447b28cfd206caec5cae169e329881041892fc2faac268b1a4dc0e31
Timestamp: 1737762884 Timestamp [UCT]: 2025-01-24 23:54:44 Age [y:d:h:m:s]: 00:326:11:47:26
Block: 1204622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230922 RingCT/type: yes/0
Extra: 011c5f8de5447b28cfd206caec5cae169e329881041892fc2faac268b1a4dc0e31021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3725c68c29fb3a0f2fc3036f617812cb0ebd6d6cdfc422e08c7149c311fc29bf 0.600000000000 1691313 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": 1204632, "vin": [ { "gen": { "height": 1204622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3725c68c29fb3a0f2fc3036f617812cb0ebd6d6cdfc422e08c7149c311fc29bf" } } ], "extra": [ 1, 28, 95, 141, 229, 68, 123, 40, 207, 210, 6, 202, 236, 92, 174, 22, 158, 50, 152, 129, 4, 24, 146, 252, 47, 170, 194, 104, 177, 164, 220, 14, 49, 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