Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41637cbbaa5c94920ab0e3a8ea7c1d47427d6d2a5464c42cb7318715d34dd7ef

Tx prefix hash: a581bacb9105ee2e42ff4ee5599f31f98798fe7fdd2af43621d07265d4664d14
Tx public key: 902996a6133a7bc73b718ccfa17eac5e26b46ba42c1e1c7982f99d000a7c72a0
Timestamp: 1704721466 Timestamp [UCT]: 2024-01-08 13:44:26 Age [y:d:h:m:s]: 01:305:06:10:18
Block: 930884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476981 RingCT/type: yes/0
Extra: 01902996a6133a7bc73b718ccfa17eac5e26b46ba42c1e1c7982f99d000a7c72a002110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c6213e68dad2ec79ba56a6f0f8c6e1436ea3522097f3a9385412811c4de3898 0.600000000000 1388774 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": 930894, "vin": [ { "gen": { "height": 930884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c6213e68dad2ec79ba56a6f0f8c6e1436ea3522097f3a9385412811c4de3898" } } ], "extra": [ 1, 144, 41, 150, 166, 19, 58, 123, 199, 59, 113, 140, 207, 161, 126, 172, 94, 38, 180, 107, 164, 44, 30, 28, 121, 130, 249, 157, 0, 10, 124, 114, 160, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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