Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798bf279c1cb5db12473c72ea1eb10eb92d9b386fdf84a23e6a4ddcbe4175aa9

Tx prefix hash: b7915bca14ace7a26076111aafc67b6a9d7e2e503c3b1fcc78d95f6fe1624891
Tx public key: ae9ad23abc4979367feba57a929ce28aa871f12a01232eeebdba5a8ddd909808
Timestamp: 1724275890 Timestamp [UCT]: 2024-08-21 21:31:30 Age [y:d:h:m:s]: 00:218:05:53:04
Block: 1093010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155829 RingCT/type: yes/0
Extra: 01ae9ad23abc4979367feba57a929ce28aa871f12a01232eeebdba5a8ddd909808021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcc5e4c907e439c1532bf79e5d5075e93fc1a58606def885a4eb4a1e35065e10 0.600000000000 1567869 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": 1093020, "vin": [ { "gen": { "height": 1093010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcc5e4c907e439c1532bf79e5d5075e93fc1a58606def885a4eb4a1e35065e10" } } ], "extra": [ 1, 174, 154, 210, 58, 188, 73, 121, 54, 127, 235, 165, 122, 146, 156, 226, 138, 168, 113, 241, 42, 1, 35, 46, 238, 189, 186, 90, 141, 221, 144, 152, 8, 2, 17, 0, 0, 0, 7, 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