Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ca69aa758f03b8d808af3ebcd62c455e9a9deda117514a979470dc7104a63df

Tx prefix hash: bd06bc9bc3dcc2030b2e75782bee1e58f9e2b12521e358c9536f50cce76b63dd
Tx public key: b8891ccadb6a87da681a8ec69d7a47bd4eb8712065a6e0f15d99e353aee246b5
Timestamp: 1725514636 Timestamp [UCT]: 2024-09-05 05:37:16 Age [y:d:h:m:s]: 00:214:21:37:34
Block: 1103273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153420 RingCT/type: yes/0
Extra: 01b8891ccadb6a87da681a8ec69d7a47bd4eb8712065a6e0f15d99e353aee246b502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fcf5991894a2e13bf9d286c49ee320bd770c80593d5993aa3e6123f9d482fa0 0.600000000000 1580040 of 15

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": 1103283, "vin": [ { "gen": { "height": 1103273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fcf5991894a2e13bf9d286c49ee320bd770c80593d5993aa3e6123f9d482fa0" } } ], "extra": [ 1, 184, 137, 28, 202, 219, 106, 135, 218, 104, 26, 142, 198, 157, 122, 71, 189, 78, 184, 113, 32, 101, 166, 224, 241, 93, 153, 227, 83, 174, 226, 70, 181, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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