Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb6d57b16d40f0a7be463e0747630bf4cb380a00aa866293c7b3c71ed06434db

Tx prefix hash: 39e5d8b93855ba1204be78c31a51debda7cef1f088390dd0503c297e8d0365d7
Tx public key: 25d8e0850a9cf0f457573ca9f9ac68d7035c08e49676c1c22885cab056775e0f
Timestamp: 1713794869 Timestamp [UCT]: 2024-04-22 14:07:49 Age [y:d:h:m:s]: 01:015:01:45:56
Block: 1006111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271723 RingCT/type: yes/0
Extra: 0125d8e0850a9cf0f457573ca9f9ac68d7035c08e49676c1c22885cab056775e0f0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67e25dd215dc45e3fd401879f06c8dd9aab1f5066945e2148f4fd2212eeb4608 0.600000000000 1467033 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": 1006121, "vin": [ { "gen": { "height": 1006111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67e25dd215dc45e3fd401879f06c8dd9aab1f5066945e2148f4fd2212eeb4608" } } ], "extra": [ 1, 37, 216, 224, 133, 10, 156, 240, 244, 87, 87, 60, 169, 249, 172, 104, 215, 3, 92, 8, 228, 150, 118, 193, 194, 40, 133, 202, 176, 86, 119, 94, 15, 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