Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6aa51519ee4a2eda6d96865c5fbce9370492da358a1dd1f79269de8f3a99a00

Tx prefix hash: abe1d451fa309ee0af8ad02d2416c8605491c681ee2021efdfd34175669af064
Tx public key: ab95be9fa6b5ee17139326bf1e4b94d1ffc9525a1ca46b3f1e6fe187c72c0a02
Timestamp: 1673464122 Timestamp [UCT]: 2023-01-11 19:08:42 Age [y:d:h:m:s]: 02:299:07:56:36
Block: 672607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733313 RingCT/type: yes/0
Extra: 01ab95be9fa6b5ee17139326bf1e4b94d1ffc9525a1ca46b3f1e6fe187c72c0a0202110000000452542ceb000000000000000000

1 output(s) for total of 3.625548757000 dcy

stealth address amount amount idx
00: 8063ab3d18554bb1cab4d27cd4f546de8a485f6b6a31e37af0b8375664d7cf15 3.625548757000 1114168 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": 672617, "vin": [ { "gen": { "height": 672607 } } ], "vout": [ { "amount": 3625548757, "target": { "key": "8063ab3d18554bb1cab4d27cd4f546de8a485f6b6a31e37af0b8375664d7cf15" } } ], "extra": [ 1, 171, 149, 190, 159, 166, 181, 238, 23, 19, 147, 38, 191, 30, 75, 148, 209, 255, 201, 82, 90, 28, 164, 107, 63, 30, 111, 225, 135, 199, 44, 10, 2, 2, 17, 0, 0, 0, 4, 82, 84, 44, 235, 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