Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6afe07b52aa60ab7724f07e7805d01536c00712cb820250d1835f4aa2d74d82f

Tx prefix hash: 3c5eb1051a0a9aeb8c09e77566d33379d8a06a5c1d5a8a58c8af725d30b8e1c6
Tx public key: 0bde1029d227ccf589ceb3b69c71b5aafad907355b2f16e7fb453562737779f1
Timestamp: 1723939260 Timestamp [UCT]: 2024-08-18 00:01:00 Age [y:d:h:m:s]: 00:255:17:34:15
Block: 1090221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182645 RingCT/type: yes/0
Extra: 010bde1029d227ccf589ceb3b69c71b5aafad907355b2f16e7fb453562737779f1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69bcbd52094e860c22ecd69ad1fbc498de4081beef3320a03b90e690869e712d 0.600000000000 1564844 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": 1090231, "vin": [ { "gen": { "height": 1090221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69bcbd52094e860c22ecd69ad1fbc498de4081beef3320a03b90e690869e712d" } } ], "extra": [ 1, 11, 222, 16, 41, 210, 39, 204, 245, 137, 206, 179, 182, 156, 113, 181, 170, 250, 217, 7, 53, 91, 47, 22, 231, 251, 69, 53, 98, 115, 119, 121, 241, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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