Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f5ca1b884eac6480566d95a8d96fbce1e897909d03c0e4c23492aa1877fd9a6

Tx prefix hash: 0dc86460543f6181a8b44ebcd96b3fefc76a39b5b730dd71314bbf87327a5605
Tx public key: 5b316b0c92c9161b81640909ece9c48b1e49cb32444ccbd66e2c3736965a3354
Timestamp: 1723567917 Timestamp [UCT]: 2024-08-13 16:51:57 Age [y:d:h:m:s]: 00:237:07:19:48
Block: 1087139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169463 RingCT/type: yes/0
Extra: 015b316b0c92c9161b81640909ece9c48b1e49cb32444ccbd66e2c3736965a335402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59572f1179d6a9de248897abf0c972f422dc921dcce49fddb9894d18325c9003 0.600000000000 1561744 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": 1087149, "vin": [ { "gen": { "height": 1087139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59572f1179d6a9de248897abf0c972f422dc921dcce49fddb9894d18325c9003" } } ], "extra": [ 1, 91, 49, 107, 12, 146, 201, 22, 27, 129, 100, 9, 9, 236, 233, 196, 139, 30, 73, 203, 50, 68, 76, 203, 214, 110, 44, 55, 54, 150, 90, 51, 84, 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