Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 830a27e7dd25f440d129c0157761c47620b400921c2c29d0193ed2bd18204c77

Tx prefix hash: bf6af5349643d1ca8845dc94dfc27b8ff30b3d4a4d77bd620cab308a32f6371c
Tx public key: 86c5fd370a28c9053a59afb76a59c266614400a67b0d08bf491a2b464a456495
Timestamp: 1699566989 Timestamp [UCT]: 2023-11-09 21:56:29 Age [y:d:h:m:s]: 01:145:15:12:20
Block: 888157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365266 RingCT/type: yes/0
Extra: 0186c5fd370a28c9053a59afb76a59c266614400a67b0d08bf491a2b464a456495021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.700151430000 dcy

stealth address amount amount idx
00: 5b7d20b359c023735f30ef42b2aa6076d99d02b4aa3b43e2ba1116053b3b5d97 0.700151430000 1344082 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": 888167, "vin": [ { "gen": { "height": 888157 } } ], "vout": [ { "amount": 700151430, "target": { "key": "5b7d20b359c023735f30ef42b2aa6076d99d02b4aa3b43e2ba1116053b3b5d97" } } ], "extra": [ 1, 134, 197, 253, 55, 10, 40, 201, 5, 58, 89, 175, 183, 106, 89, 194, 102, 97, 68, 0, 166, 123, 13, 8, 191, 73, 26, 43, 70, 74, 69, 100, 149, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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