Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dcfd2f887d64fe29216a0537ecb5b811bd8eb4eb9ef0d5821940af6f43b2007

Tx prefix hash: 1a514b9e345aecaa5494685c2d8d583ca93ea2aa5075cf5029d88b87dca370ac
Tx public key: 5fcd13dc818be9ec12c627882ee25b96f4f256275a50ae528ff32fe1b5876701
Timestamp: 1698159208 Timestamp [UCT]: 2023-10-24 14:53:28 Age [y:d:h:m:s]: 01:090:10:12:49
Block: 876700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325811 RingCT/type: yes/0
Extra: 015fcd13dc818be9ec12c627882ee25b96f4f256275a50ae528ff32fe1b587670102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.764062670000 dcy

stealth address amount amount idx
00: 0e60c517cf66466c669c26ac2128e2272d0a2279f5afff94d1cc1330c4218158 0.764062670000 1332040 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": 876710, "vin": [ { "gen": { "height": 876700 } } ], "vout": [ { "amount": 764062670, "target": { "key": "0e60c517cf66466c669c26ac2128e2272d0a2279f5afff94d1cc1330c4218158" } } ], "extra": [ 1, 95, 205, 19, 220, 129, 139, 233, 236, 18, 198, 39, 136, 46, 226, 91, 150, 244, 242, 86, 39, 90, 80, 174, 82, 143, 243, 47, 225, 181, 135, 103, 1, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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