Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6adf1c3e19d5ed4ad0099457d2e4a2112a4cdb9a1424737eb8d1a80a40cd0bc9

Tx prefix hash: 71d769a31a58b78381f9a26314f01600578d5cabd1900acb7b46d747992eddf3
Tx public key: 487c7670e91fd7eefa7d791d0bd440f12786322743f5263395c0cda8e88238eb
Timestamp: 1656814921 Timestamp [UCT]: 2022-07-03 02:22:01 Age [y:d:h:m:s]: 02:184:14:10:49
Block: 535453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653255 RingCT/type: yes/0
Extra: 01487c7670e91fd7eefa7d791d0bd440f12786322743f5263395c0cda8e88238eb02110000000ca8c141c5000000000000000000

1 output(s) for total of 10.323384127000 dcy

stealth address amount amount idx
00: 1362b67171d451d21cc195322a30a3b577b6e57a4c3381b1c7fa028cc110d533 10.323384127000 965086 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": 535463, "vin": [ { "gen": { "height": 535453 } } ], "vout": [ { "amount": 10323384127, "target": { "key": "1362b67171d451d21cc195322a30a3b577b6e57a4c3381b1c7fa028cc110d533" } } ], "extra": [ 1, 72, 124, 118, 112, 233, 31, 215, 238, 250, 125, 121, 29, 11, 212, 64, 241, 39, 134, 50, 39, 67, 245, 38, 51, 149, 192, 205, 168, 232, 130, 56, 235, 2, 17, 0, 0, 0, 12, 168, 193, 65, 197, 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