Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67d40dfc5c14f6637f4c7150fc0b083a8b2191fea40697303ab101ba9adc54e8

Tx prefix hash: 42418565f2639ed8e1d56c94337c158a9192f8fd64a5b35d253efe8055235a8e
Tx public key: 93036b7eaedb34e0f57aad72e53d8fd53e7ec1e174f986519b5014748fd24fc2
Timestamp: 1658920782 Timestamp [UCT]: 2022-07-27 11:19:42 Age [y:d:h:m:s]: 02:327:01:03:14
Block: 552785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 754871 RingCT/type: yes/0
Extra: 0193036b7eaedb34e0f57aad72e53d8fd53e7ec1e174f986519b5014748fd24fc202110000000133af99f4000000000000000000

1 output(s) for total of 9.044695517000 dcy

stealth address amount amount idx
00: 28bbdaed96cee43111e5611f9124a266b08c77a18d95130b0a1fb0a5f695188f 9.044695517000 984535 of 0

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": 552795, "vin": [ { "gen": { "height": 552785 } } ], "vout": [ { "amount": 9044695517, "target": { "key": "28bbdaed96cee43111e5611f9124a266b08c77a18d95130b0a1fb0a5f695188f" } } ], "extra": [ 1, 147, 3, 107, 126, 174, 219, 52, 224, 245, 122, 173, 114, 229, 61, 143, 213, 62, 126, 193, 225, 116, 249, 134, 81, 155, 80, 20, 116, 143, 210, 79, 194, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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