Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b351e2179fbea760fb976853b2b723c36827feaf2cb4a3d80b59f699aec8b68

Tx prefix hash: 202052f815b398caf2770c039d5ebdcb3d33a2c14cc35425c0d5941a567366ab
Tx public key: c2c1a4187eb492920c2254d34f41061887f357eae14a6b65440c0739715e3126
Timestamp: 1705897428 Timestamp [UCT]: 2024-01-22 04:23:48 Age [y:d:h:m:s]: 01:318:17:43:52
Block: 940600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486660 RingCT/type: yes/0
Extra: 01c2c1a4187eb492920c2254d34f41061887f357eae14a6b65440c0739715e31260211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fc37ab3b55173f1cb57f90293af713360a182b307e91b54796c79e4dd0d0aff 0.600000000000 1398738 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": 940610, "vin": [ { "gen": { "height": 940600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fc37ab3b55173f1cb57f90293af713360a182b307e91b54796c79e4dd0d0aff" } } ], "extra": [ 1, 194, 193, 164, 24, 126, 180, 146, 146, 12, 34, 84, 211, 79, 65, 6, 24, 135, 243, 87, 234, 225, 74, 107, 101, 68, 12, 7, 57, 113, 94, 49, 38, 2, 17, 0, 0, 0, 9, 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