Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef5e95e00d8cb6d8616e795e4b902ac61a0926eb8b8f24ff3a5bb752bc166477

Tx prefix hash: c0c63aadd2ec4d5f1ca2313adc0266636ba91654f5d72b2b02ad8a8e1f33d5cb
Tx public key: dccfe4cef6fdd00b41f64d2135a78ee2eb5e6064398032aad8e37036c94aa2ed
Timestamp: 1733894454 Timestamp [UCT]: 2024-12-11 05:20:54 Age [y:d:h:m:s]: 00:099:05:06:08
Block: 1172656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70703 RingCT/type: yes/0
Extra: 01dccfe4cef6fdd00b41f64d2135a78ee2eb5e6064398032aad8e37036c94aa2ed021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab3c0edda7154b2f8309a24116f396104f0530909944e867ccbddfc36f1f999c 0.600000000000 1658577 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": 1172666, "vin": [ { "gen": { "height": 1172656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab3c0edda7154b2f8309a24116f396104f0530909944e867ccbddfc36f1f999c" } } ], "extra": [ 1, 220, 207, 228, 206, 246, 253, 208, 11, 65, 246, 77, 33, 53, 167, 142, 226, 235, 94, 96, 100, 57, 128, 50, 170, 216, 227, 112, 54, 201, 74, 162, 237, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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