Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bf7c351c7bd7d7404bcb7c758906cf6d2f31c40a6a201601c4f0656062de433

Tx prefix hash: f525604c97cc5ba8e6747d34c98b57cee35dc802488faef63e8b2f673447a1c6
Tx public key: 9f5c8efe8d686dcd99b62c9c17413dd5f24455c2f36316295b9d43f49dbb38e5
Timestamp: 1650517690 Timestamp [UCT]: 2022-04-21 05:08:10 Age [y:d:h:m:s]: 03:194:11:02:50
Block: 484732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 917315 RingCT/type: yes/0
Extra: 019f5c8efe8d686dcd99b62c9c17413dd5f24455c2f36316295b9d43f49dbb38e5021100000006bf7ee4e7000000000000000000

1 output(s) for total of 15.201340606000 dcy

stealth address amount amount idx
00: f6353e474540928ce2cb2a93c674231a03d82a2fd405cb68e582c6a728ef6ee5 15.201340606000 906657 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": 484742, "vin": [ { "gen": { "height": 484732 } } ], "vout": [ { "amount": 15201340606, "target": { "key": "f6353e474540928ce2cb2a93c674231a03d82a2fd405cb68e582c6a728ef6ee5" } } ], "extra": [ 1, 159, 92, 142, 254, 141, 104, 109, 205, 153, 182, 44, 156, 23, 65, 61, 213, 242, 68, 85, 194, 243, 99, 22, 41, 91, 157, 67, 244, 157, 187, 56, 229, 2, 17, 0, 0, 0, 6, 191, 126, 228, 231, 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