Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e45d5e653f5e4879da642e1cab80d0afd312fddb48470daa46f48b15d109c62a

Tx prefix hash: 562ac051d02b0e95a4f21ffddd542bd73167f5c9967dbad0f82429dfb3a30195
Tx public key: b0ea83c13fa46edf9c7d69fd32401bc8d1bd9ffb5b34aeb567a6725d5cbaf10d
Timestamp: 1695463968 Timestamp [UCT]: 2023-09-23 10:12:48 Age [y:d:h:m:s]: 01:192:04:52:35
Block: 854339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398436 RingCT/type: yes/0
Extra: 01b0ea83c13fa46edf9c7d69fd32401bc8d1bd9ffb5b34aeb567a6725d5cbaf10d02110000000a33af99f4000000000000000000

1 output(s) for total of 0.906192139000 dcy

stealth address amount amount idx
00: d121186fb62438aaf97e28b646c4bca569d795544aa0e32477679824a7dacd76 0.906192139000 1308307 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": 854349, "vin": [ { "gen": { "height": 854339 } } ], "vout": [ { "amount": 906192139, "target": { "key": "d121186fb62438aaf97e28b646c4bca569d795544aa0e32477679824a7dacd76" } } ], "extra": [ 1, 176, 234, 131, 193, 63, 164, 110, 223, 156, 125, 105, 253, 50, 64, 27, 200, 209, 189, 159, 251, 91, 52, 174, 181, 103, 166, 114, 93, 92, 186, 241, 13, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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