Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d78f78f2004f150cf67bc7b3c5b1bf37b268504fb6c024969006d5acd826b646

Tx prefix hash: 115284a14d7a04976b1eb67daeb75880640f34c6f43853be022e00693f26a59d
Tx public key: bc7c83d0ac42e53c416c31e34d5323334f27f4e503bfa2ebcc3c4e010e2f8bf6
Timestamp: 1677005461 Timestamp [UCT]: 2023-02-21 18:51:01 Age [y:d:h:m:s]: 02:055:12:48:23
Block: 701987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561284 RingCT/type: yes/0
Extra: 01bc7c83d0ac42e53c416c31e34d5323334f27f4e503bfa2ebcc3c4e010e2f8bf602110000000174b6d784000000000000000000

1 output(s) for total of 2.897514185000 dcy

stealth address amount amount idx
00: abbde0b326cb834b09b0caf72e4cbb67b2f504725b9d3a0cb272a23e1c9e5569 2.897514185000 1145482 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": 701997, "vin": [ { "gen": { "height": 701987 } } ], "vout": [ { "amount": 2897514185, "target": { "key": "abbde0b326cb834b09b0caf72e4cbb67b2f504725b9d3a0cb272a23e1c9e5569" } } ], "extra": [ 1, 188, 124, 131, 208, 172, 66, 229, 60, 65, 108, 49, 227, 77, 83, 35, 51, 79, 39, 244, 229, 3, 191, 162, 235, 204, 60, 78, 1, 14, 47, 139, 246, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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