Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa30adc8ef7f7833464ce4a1e914629ce84ad42827b4540519f484887fbfb445

Tx prefix hash: 281bc4e1bfa9e71fcb45662c0c1d564d8b5060a2842a6ce9ba685a9caf18e897
Tx public key: 4505e8ff8a09240f046f5a17a5ad1ae3ad4f24668b53dd98fb21811f62b48fc6
Timestamp: 1705564041 Timestamp [UCT]: 2024-01-18 07:47:21 Age [y:d:h:m:s]: 01:298:00:23:30
Block: 937853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471812 RingCT/type: yes/0
Extra: 014505e8ff8a09240f046f5a17a5ad1ae3ad4f24668b53dd98fb21811f62b48fc60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5215a9a6f2f2d91df6c6340bc52922fb86d9e231e9ef82ea2cb477a67d73d1 0.600000000000 1395917 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": 937863, "vin": [ { "gen": { "height": 937853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5215a9a6f2f2d91df6c6340bc52922fb86d9e231e9ef82ea2cb477a67d73d1" } } ], "extra": [ 1, 69, 5, 232, 255, 138, 9, 36, 15, 4, 111, 90, 23, 165, 173, 26, 227, 173, 79, 36, 102, 139, 83, 221, 152, 251, 33, 129, 31, 98, 180, 143, 198, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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