Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8328ff15f4b28ffeb3d393d7efe4d41f465b1e7cd55a9e7adf733f9ff07885d

Tx prefix hash: 5140988cae4580c9e926df8a575f8aca86ae776028f57cc5e480f29d450e2a7b
Tx public key: c4e4461dc97511bc8a753eef8cc1ad7bc32453663381d52db40ff61d59b880ef
Timestamp: 1703132362 Timestamp [UCT]: 2023-12-21 04:19:22 Age [y:d:h:m:s]: 01:319:01:49:22
Block: 917732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486862 RingCT/type: yes/0
Extra: 01c4e4461dc97511bc8a753eef8cc1ad7bc32453663381d52db40ff61d59b880ef0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48df7afd76198a590e354263ac4529ec070dd183e1bb64b13827e0b0ac0a27ab 0.600000000000 1375314 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": 917742, "vin": [ { "gen": { "height": 917732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48df7afd76198a590e354263ac4529ec070dd183e1bb64b13827e0b0ac0a27ab" } } ], "extra": [ 1, 196, 228, 70, 29, 201, 117, 17, 188, 138, 117, 62, 239, 140, 193, 173, 123, 195, 36, 83, 102, 51, 129, 213, 45, 180, 15, 246, 29, 89, 184, 128, 239, 2, 17, 0, 0, 0, 4, 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